You are missing the point of the archive.
The archive will contain your entire setup including dependencies on resources and other artifacts - it is much more than a standard .ear:
myapp.cli:
- startup.scr
- shutdown.scr
- int1.rar
- int2.rar
- services.sar
- myapp.ear
- admin.war
The archive will install the needed resources (datasources, JMS queues, ...), then the two .rar files which etablish connections to external EIS' (maybe the script even changes the config of those too), then the .sar, then the .ear and finally the .war.
shutdown.scr makes sure that everything is done in the reverse order on undeploy.
And yes, I agree that JBoss Tools should support building / deploying such an archive.