Failover of clustered bean invocations might not happen if the client itself is a server instance and the client server had a local deployment handling the invocation

Currently, if a stateful bean is @Cluster(ed) and an invocation on it is done from within the same server, invocations on that bean are always handled by the LocalEJBReceiver even if the cluster has multiple others nodes hosting that stateful bean.

The LocalEjbReceiver currently receives the cluster topology but doesn't create (remote) EJB receviers out of it for the client context. The missing piece is configurations that need to be passed for creating the remote EJB receivers.