Duplicate nodes in JMX tree makes tree hard to navigate

steps to reproduce:

1. EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
2. EXEC: create a server adapter for it
3. ASSERT: your server adapter now has a JMX child node
4. EXEC: double click it and wait until all MBeans are loaded
5. EXEC: now try to see if you can find your deployment

Result:
You get a listing of tons of beans.

Your deployment is a child bean of jboss.as, named by the war that was created:

Rather painfull to find a listing of your deployments in this way.