Deployment of POJO WS fails silently when WAR includes JSR 181 API jar

Deploying a POJO WS fails silently in EAP 5.0 if the WAR contains the JSR 181 API library (jsr-181-api.jar) in WEB-INF/lib. Removing the library fixes the problem and the POJO WS is deployed successfully. This is worth looking into for two reasons:

1) There is no indication during deployment that anything has gone wrong. An exception is thrown when you try and access the WS endpoint, but it's of little use to the end user/developer (ClassCastException).
2) The same WAR deploys successfully to EAP 4.3, which brings up the question of whether this is intended behavior or not.

I have attached a WAR file (PojoWS.war) to this JIRA that can be used to reproduce the issue. I have also attached the maven project (pojows.zip) which includes the source for the POJO WS.

Deploying on EAP 5.0
======================================================

• The only output to the console and server log (no errors):
  17:04:34,567 INFO [TomcatDeployment] deploy, ctxPath=/PojoWS

• JBoss WS status page shows:
  "There are currently no endpoints deployed"

• Trying to access the SOAP endpoint yields (full stack attached):
  java.lang.ClassCastException: com.examples.PojoWS cannot be cast to javax.servlet.Servlet

Deploying on EAP 4.3
======================================================

• Output to console and server.log:
  17:12:25,244 INFO [DefaultEndpointRegistry] register: jboss.ws:context=PojoWS,endpoint=PojoWS
  17:12:25,322 INFO [TomcatDeployer] deploy, ctxPath=/PojoWS, warUrl=.../tmp/deploy/tmp1372051770419075568PojoWS-exp.war/
  17:12:26,292 INFO [WSDLFilePublisher] WSDL published to: file:/NotBackedUp/kbabo/sandbox/eap/jboss-eap-4.3/jboss-as/server/default/data/wsdl/PojoWS.war/PojoWSService7825882996266336424.wsdl

• JBoss WS status page shows:
  http://localhost:8080/jbossws/services
  Endpoint Name jboss.ws:context=PojoWS,endpoint=PojoWS
  Endpoint Address http://127.0.0.1:8080/PojoWS/pojo?wsdl