Server log messages does not reflect the use of "distinct" naming for EJB's

If an application (jboss-ejb3.xml) or server configuration is marked with the distinct flag
<jboss:ejb-jar .... version="3.1" impl-version="2.0">
<distinct-name>WOLF</distinct-name>
</jboss:ejb-jar>

The client need to use the the correct lookup with distinct name
"ejb:MyEAR/MyEjbJar/WOLF/MyBean!MyInterface
to get the bean proxy.

Unfortunately there is no hint whether an application is marked with this distinct flag.
The server log still show the same output as without like this:

INFO WFLYEJB0473: JNDI bindings for session bean named 'SimpleBean' in deployment unit 'subdeployment "ejb.jar" of deployment "EAP71-PLAYGROUND-server.ear"' are as follows:
java:global/EAP71-PLAYGROUND-server/ejb/SimpleBean!org.jboss.wfink.eap71.playground.Simple

It would be good if the log message show the correct JNDI name or a hint that the EJB has a distinct name applied.