Thanks for the quick reply. I have read thru this and it does seem to match my situation. I also reviewed JIRA and unfortunately for me, it looks like this was fixed in AS5.1.x (and presumably beyond) but that doesn't help me sitting on JBoss 4.2.3. I posted a comment on one of the Jira entries asking for clarification but I sure looks like nothing in 4.2.3.
I've been doing some more testing and I swear it appears as thru JBoss 4.2.3 is handling SOME of the cases where a remote proxy is retrieved and we want to run locally. It seems like the couple cases we have seen may have been triggered on the server thru JMS rather than a client making a remote call. I have debugged client and server code and seen the proxy class returned as StatelessRemoteProxy and yet still works locally without having to get the local interface rather than the remote.
Don't get me wrong, this is a GOOD thing - except I need to know how to identify the specific cases that may fail!