Replicating JNDI tree to another server

Description of problem:
This use case is taken from one of our user which we were able to handle using HA-JNDI in EAP 5:
1. JMS Client will create Context with two URL (node1, node2) (java.naming.provider.url property)
2. For some reason client is connected to node2 first which will have no JMS admin objects registered in JNDI (this happens when this node is configured as HornetQ backup)
3. Node2 has replicated JNDI tree from node1. So connection factory will connect client to node1 and queue/topics are deployed on node1.

Can be this functionality provided in EAP 6, please?