The dynamic class loading in the current remoting framework is just broken. It cannot handle loading classes outside of its codebase. Just using the thread context class loader is not adequate as this is not typically set correctly until the invocation has been dispatched to the application context. The class loading in the remoting framework is being overhauled along with the framework itself to be consistent with the rest of the microkernel in jboss 5.
Think is refering to org.jboss.remoting.AbstractInvoker. Will fix. Thanks.