JndiSessionRegistrarBase registers EJBs with @RemoteBinding twice

JndiSessionRegistrarBase registers the EJB's ProxyFactory, then immediately unbinds and registers it again.

This causes problems in ProxyClusteringRegistry because the register call sets up a map of cluster members, which is referenced
from the EJB's ReplicantsManagerInterceptor. The unbind then deletes this map in ProxyClusteringRegistry, and the 2nd
register creates a new map that will get updates when the cluster membership changes.
Since the interceptor now has a reference to a different map, it never sees the cluster membership changes.