Hi is that really true: anonymous wrote : and this CL does not support loading bytes from a remote location (which would be required for this use case). I tried to lookup an session bean from which i only have one @Remote interface in my class loader (ie. in the ear or in the unit test runner). That session bean implements other @Remote interfaces. But i dont care for them. My code is like the user of the factory pattern: InitialContext().lookup() ist the factory, i get an session bean, i communicate with it across the one @Remote interface known to me. Reason why the other @Remote interface needs to be loaded is that the deserialized statelessproxystub references it in its internals. When I activate remote class loading ... i can see that the referenced session bean interfaces get remotely downloaded... but they are not available for the container that hosts the referencing session bean. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178689#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...