Hmmm. No answers. Yet it seems that this is fundamental, since if the back-end addresses are being put into the WSDL, and if the back-end is not visible to the client, then automated tools (e.g. SOAP-UI) will not work correctly.
Fortunately I found what I believe to be the answer in a post to the Web Services community: https://community.jboss.org/message/524256
In the 6th entry there (from Robert Crank) he directs us to jboss-beans.xml. That file contains the address and port to use when re-writing the address to use. Setting these values causes them to be used in both schema-location references and in the endpoint location, as required.
With that fix all is well in the world again ;-)
Hmmm. The SOAPProxy action, when it creates WSDL for itself, will respect these properties:
if defined in your server's deploy/jbossesb.sar/jbossesb-properties.xml file, in the "transports" section. The WSDL will then have all it's soap:address locations transformed to use the specified host and/or ports.
If you are not satisfied with the solution you found, and would like the above capability to be extended to other ESB-generated WSDL's, please feel free to add a Jira Feature Request (or maybe this could be viewed as a Bug...) here: