Batch jobs in a sub-deployment can be started but not queried

In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute JobOperator.getJobInstance() from the WAR on the same job.

Visibility should be consistent for starting and querying batch jobs.

More details on https://github.com/jberet/jsr352/issues/105.