Not sure if this was what Scott meant, but the dependencies come via the Remoting.makeRemotable(InstanceAdvised proxy, InvokerLocator locator, Object objectId) method, which AFAICT isn't used anywhere. If someone wanted to get the same functionality they can create the equivalent interceptor list and call makeRemotable(InstanceAdvised proxy, InvokerLocator locator, Object objectId, List interceptors, String subsystem). So drop the convenience method. If you're concerned about dropping the method in a CR2, copy the class back to the AS project aspects module. Then create a different class in remoting-aspects, e.g. RemotingUtil with the same behavior x-the offending method. The class in the aspects module delegates to RemotingUtil. There was an equivalent class in aspects called ClusteredRemoting. Had same problem and no one was using it. When I pulled the clustering stuff out of aspects I just left that one there in case an end user wanted it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166837#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...