I stumbled across this several times as well.
If you come up with a solution that would be perfect.
The only problem i see here is the disconnecgt between the MC and the JMX kernel. That particular attribute is managed by the MC. I think it should somehow be populated when the ServiceEndpointManager is initialized and not just bypassed when the WSDL is delivered.
I have commited an implementation for this.
I have added a couple of methods to the ServerConfig interface so that these two values can be retrieved. For the JBoss implementation I query the MBean server for all connectors and return the port for the first one that is secured and the port for the first one that is not secured.
Within the ServiceEndpointManager if the ports have not already been set I retrieve the ServerConfig using the factory and lookup these two values.
I have not been able to implement the Tomcat versions of these methods yet as I can not get the latest JBossWS to deploy on Tomcat, however I believe the approach should be similar so I can raised the following task: -