Mark EJB's as clustered by using the jboss-ejb3.xml deployment descriptor seems to work not correct in any case

Issue

If enterprise beans in an application are marked as clustered with the jboss-ejb3.xml deployment descriptor (DD)

<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee"
                  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security"
                  xmlns:c="urn:clustering:1.0" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
                     http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
                  version="3.1" impl-version="2.0">
  <enterprise-beans>
  </enterprise-beans>
  <assembly-descriptor>
    <c:clustering>
      <ejb-name>Bean1</ejb-name>
      <ejb-name>Bean2</ejb-name>
      <ejb-name>Bean3</ejb-name>
      <c:clustered>true</c:clustered>
    </c:clustering>
  </assembly-descriptor>
</jboss:ejb-jar>

The bean seems to be clustered as the invocation from a client will be load balanced and the beans are invoked in different JBoss instances.

But if a ClusterNodeSelector will be registered at the client side with the remote.cluster..clusternode.selector the selector will only be invoked for the last registered bean (Bean3 in this example)