Add the "jboss.naming.client.ejb.context" property with a value of true to those properties:
That tells the remote naming implementation to setup the EJB client context with a EJB receiver that makes use of the same connection that the remoting naming implementation used to connect to the remote server.
Dances a jig with joy.
Load Balanced Clustering and thread safe remote EJB lookup all working in the same day - is it Christmas ?
Unfortunately adding the "jboss.naming.client.ejb.context" property didn't make any difference to me.
I have tried every example I can find and can't get any of them to work. I had everything running well under AS 7.2, but when I tried to shift over to the new EAP 6.1, it won't connect. Any other suggestions on what to try?