If you change remoting & other stuff it will probably work, but then it won't be a JBAS 4.0.5.GA any more, and it is hard to support that... but anyone can try at his own risk.
Why won't it be 4.0.5.GA anymore? I said I'll deploy JBM in its own scoped bubble, not change AS dependencies.
You may have luck scoping on the server side, but the main problems are on the client side (where you can't scope).
You'll need to have the JBM latest versions of remoting on the client classpath before anything else, and this may not work well with the other things from JBAS 4.0.5 which need a different version of remoting etc (e.g. EJB3 or webservices).
If you don't need EJB3 or web services then you might be ok.