mod_cluster with WildFly reports 0.0.0.0 to the balancer

While I was working on issue 138 (MODCLUSTER-448), it came to my attention that one can't force EAP 6.4 Beta (jbossweb, mod_cluster 1.2.11) to send anything like ajp://0.0.0.0:8009 to the balancer. If one sets the application server to bind to 0.0.0.0, mod_cluster core correctly guesses 127.0.0.1 and sends ajp://127.0.0.1:8009 to the balancer.
On the contrary, WildFly goes only half way: it reports 127.0.0.1 in the log:

[org.jboss.modcluster] (UndertowEventHandlerAdapter - 1) MODCLUSTER000012: default-server connector will use /127.0.0.1

and yet it sends 0.0.0.0 to the balancer:

Node localhost (ajp://0.0.0.0:8009):

Note the localhost string in place of properly generated UUID: MODCLUSTER-451.

For some historical context, I suggest: MODCLUSTER-91 and MODCLUSTER-168