If you try to install jbossws stack on WildFly, you will notice that not all JBWS related modules are removed before the new version is deployed which results in some files redundant after upgrade and in one case in file missing.

The differences (ignoring version in filenames):
upgrade deletes org/apache/httpcomponents module, bringing back only some files
– org/apache/httpcomponents/main/httpmime-4.5.jar is missing in upgraded server
– I suppose JBWS shouldn't remove the file just like that, especially when module is used by other module (missing dependency in jbossws?)

upgrade left org/apache/santuario/xmlsec/main/xmlsec-2.0.5.jar and org/apache/ws/xmlschema/main/xmlschema-core-2.2.1.jar files in place
– modules-deploy.conf doesn't contain path for these modules to delete before upgrading

upgrade brings new jar org/apache/cxf/impl/main/cxf-rt-features-clustering.jar and new modules org/apache/cxf/services-sts, org/apache/cxf/ws-security, org/jboss/ws/cxf/sts
– WF10 has 5.1.3.Final, files added in newer versions via JBWS-3984, JBWS-3981

Files to delete listed from https://github.com/jbossws/jbossws-cxf/blob/master/modules/resources/src/main/resources/resources/modules-deploy.conf also contains masks that are not valid anymore for recent WildFly (tested WF 8.2+):

org/apache/ws/commons/xmlschema/**, 
org/jboss/ws/jaxws-jboss-httpserver-httpspi/**,
org/springframework/spring/**,

Please revisit its content regarding above issues.