Unless you need to access the TransactionManager via JNDI this should be no problem. AFAIK you can safely ignore this message.
Instinct, thanks for that. I did get some weird errors when trying to set up my connectionpool that worked fine in jboss3.x, but I'll continue investigating.
Question still stands tho, i mean the warning must pop up for a reason? Sure nothing in Jboss will try and access it through there?