I was able to solve the Maven MANIFEST (bug?) by adding the dependencies to the jboss-deployment-structure.xml file, and am updating this in case Google brings anyone else here.
<jboss-deployment-structure>
<!-- Make sub deployments isolated by default, so they cannot see each others classes without a Class-Path entry -->
<ear-subdeployments-isolated>true</ear-subdeployments-isolated>
<!-- This corresponds to the top level deployment. For a war this is the war's module, for an ear -->
<!-- This is the top level ear module, which contains all the classes in the EAR's lib folder -->
<deployment>
<!-- Exclusions allow you to prevent the server from automatically adding some dependencies
<exclusions>
<module name="org.javassist" />
</exclusions>
-->
<!-- This allows you to define additional dependencies, it is the same as using the Dependencies: manifest attribute -->
<dependencies>
<module name="org.jboss.ws.cxf.jbossws-cxf-client services export" />
<module name="org.apache.ws.xmlschema services export" />
<module name="org.apache.ws.security services export" />
</dependencies>
<!-- These add additional classes to the module. In this case it is the same as including the jar in the EAR's lib directory
<resources>
<resource-root path="my-library.jar" />
</resources>
-->
</deployment>
</jboss-deployment-structure>