JBossWS attaches interceptors to several subdeployers in order to support webservice deployment from regular archives. This happens when the service archive (jbossws.sar) gets deployed. Along with the service archive it is planned to ship other artefacts which already contain webservice descriptors and thus should be handled by the previously created (and attached) interceptor. It looks like the maindeployer, that has already picked up the service archive does ignore the recently attached interceptor when invoking deployment of the remaining artifacts that ship with the service archive as well.

The forum reference explains it in more detail and contains some log output that shows the described behavior.