The jboss-4.2.3.GA binary comes with jbossws-deploy.conf in 'all' configuration (server/all/deploy/jbossws.sar/jbossws-deploy.conf) with the following contents:

bin/wsconsume.bat bin/wsconsume.sh bin/wsprovide.bat bin/wsprovide.sh bin/wsrunclient.bat bin/wsrunclient.sh bin/wstools.bat bin/wstools.sh client/FastInfoset.jar client/jaxb-api.jar client/jaxb-impl.jar client/jaxb-xjc.jar client/jaxws-rt.jar client/jaxws-tools.jar client/jboss-jaxrpc.jar client/jboss-jaxws-ext.jar client/jboss-jaxws.jar client/jboss-saaj.jar client/jbossws-client.jar client/jbossws-common.jar client/jbossws-framework.jar client/jbossws-spi.jar client/jettison.jar client/policy.jar client/stax-api.jar client/stax-ex.jar client/streambuffer.jar client/wsdl4j.jar client/wstx.jar lib/jaxb-api.jar lib/jaxb-impl.jar server/default/lib/jboss-jaxrpc.jar server/default/lib/jboss-jaxws-ext.jar server/default/lib/jboss-jaxws.jar server/default/lib/jboss-saaj.jar server/default/lib/jbossws-common.jar server/default/lib/jbossws-framework.jar server/default/lib/jbossws-spi.jar

Please note it refers the default configuration.
This can lead to broken installation of JBossWS-Metro/CXF over the 'all' configuration.

Need to check every other containers and understand why this happened / how to fix.