I'm personally fine with jboss.as mostly because the distinction is pretty unimportant to me and this would be the first org.wildfly appearance in the EAP 6 management API. I expect that would lead to some sort of fuss and I'm not motivated enough by the name issue to spend time dealing with the fuss.

I asked Jason and his response was:

Jason T. Greene: technically he's right
Jason T. Greene: new stuff shouldn't use that name
Jason T. Greene: and the new wildfly name is going into EAP one day
Jason T. Greene: but its not really like it matters that much

So, I don't think the name thing should block this. Pedro if you want to change it, that's fine.