Deploy a simple EJB with "@Stateless @Clustered @Remote(MyRemote.class) @RemoteBinding ( jndiBinding = "foo" )" to the cluster. Call the EJB with a client. Start another cluster member. Call the EJB again. Check the client's member list. Expected result: member list is updated to include new node Actual result: member list is not updated Member list pulled from the stub with: StatelessClusteredProxyInvocationHandler ih = (StatelessClusteredProxyInvocationHandler) Proxy.getInvocationHandler(stub); FamilyClusterInfo fci = ih.getFamilyWrapper().get(); System.out.println ( fci.getTargets() );

A clustered EJB using @RemoteBinding(jndiBinding=...) or <remote-binding> incorrectly created a proxy in JNDI, then replaced it with the correct proxy. When the cluster membership changed, the wrong proxy's cluster member list was updated, so the EJB clients were not informed about the new member. The extra proxy is no longer created and removed. The cluster member list now updates correctly, allowing EJB calls to load balance and failover to the new nodes.