When a change to the cluster topology occurs, the proxies in JNDI for the affected beans are not being updated. Effect is the target list in the proxy always contains the members that were present when the bean was deployed and the proxy created.

EJB2 has a process to rebind the proxy when a topology change occurs; EJB3 probably needs something similar.