That is a legacy invoker proxy binding, which was removed in jboss-4.0.0RC2. You seem to use an old standardjboss.xml or a some custom container configuration in jboss.xml
Index: standardjboss.xml
===================================================================
RCS file: /cvsroot/jboss/jboss/src/etc/conf/default/standardjboss.xml,v
retrieving revision 1.82
retrieving revision 1.83
diff -r1.82 -r1.83
10c10
< <!-- $Id: standardjboss.xml,v 1.82 2004/07/21 16:33:37 loubyansky Exp $ -->
---
> <!-- $Id: standardjboss.xml,v 1.83 2004/07/30 17:40:28 tdiesler Exp $ -->
246,251d245
< <invoker-proxy-binding>
< <name>session-webservice-invoker</name>
< <invoker-mbean/>
< <proxy-factory>org.jboss.net.ws4ee.server.EJBProxyFactoryImpl</proxy-factory>
< <proxy-factory-config/>
< </invoker-proxy-binding>
543,544d536
< <!-- the next invoker is for additional ws transports and will be ignored when jb.net is not installed -->
< <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name>
575,576d566
< <!-- the next invoker is for additional ws transports and will be ignored when jb.net is not installed -->
< <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name>
609,610d598
< <!-- the next invoker is for additional ws transports and will be ignored when jb.net is not installed -->
< <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name>
653,654d640
< <!-- the next invoker is for additional ws transports and will be ignored when jb.net is not installed -->
< <invoker-proxy-binding-name>session-webservice-invoker</invoker-proxy-binding-name>
