jBPM5 is agnostic to the environment and you can set it up in any container or outside a container as well.
Which features of the project do you want to use? the jBPM5 core can also be embedded inside your application and used without any of the provided tooling.
Those that you mention are the core libs.
All of them are maven projects, that means that you can easily manage and get the dependency tree for all of them in order to check the dependency requirements.
For the tooling you need to know that most of the tooling is being built using GWT and can be deployed in any container, but it's not up to the jBPM5 project specify all the other containers deployment requirements. Most of the project is built using standard technologies that helps the deployment process.
Imagine the core of jBPM5 as Hibernate, that you can use it everywhere, doesn't make sense to write a document for each container, it will be good if as a community effort we can coordinate a wiki to share our experiencies with different containers.