ClassNotFoundException: org.guvnor.rest.client.CreateOrCloneRepositoryRequest

Description of problem:
Happens during REST request to clone a repository when both business-central.war and kie-server.war are deployed. Sometimes on BRMS, sometimes on BPM Suite.

Important parts of server.log:

JNDI bindings for session bean named AvailableJobsExecutor in deployment unit deployment "kie-server.war" are as follows:
...
java:module/AvailableJobsExecutor
...
JNDI bindings for session bean named AvailableJobsExecutor in deployment unit deployment "business-central.war" are as follows:
...
java:module/AvailableJobsExecutor
...
23:02:24,836 INFO [AssetMgmt] (http-/127.0.0.1:8080-4) Auto approve for request: org.guvnor.rest.client.CreateOrCloneRepositoryRequest@7b483c8
...
23:02:25,901 WARN [org.jbpm.executor.impl.AbstractAvailableJobsExecutor] (EJB default - 3) Error during command org.guvnor.rest.backend.cmd.CreateOrCloneRepositoryCmd error message org.guvnor.rest.client.CreateOrCloneRepositoryRequest from [Module "deployment.kie-server.war:main" from Service Module Loader]: java.lang.ClassNotFoundException: org.guvnor.rest.client.CreateOrCloneRepositoryRequest from [Module "deployment.kie-server.war:main" from Service Module Loader]

My impression is that AvailableJobsExecutor bean is registered twice (from business-central and kie-server) under the same JNDI binding and so the REST business-central request may be (inadvertently) handled by kie-server, which does not have guvnor-rest-client lib.

Version-Release number of selected component (if applicable):
6.2.0.ER3

How reproducible:
Some installations are affected, some are not. But once it happens, it happens every time.

Steps to Reproduce:
1. Install BRMS on EAP 6.4.3.GA.
2. Start the server in standalone mode.
3. Run:
> $ curl -s -u '<user>:<password>' -H 'Accept: application/json' -H 'Content-Type: application/json' -X POST -d '

' 'localhost:8080/business-central/rest/repositories/'

Actual results:
The REST job fails due to ClassNotFoundException.

Expected results:
The REST job should complete successfully even when kie-server.war is deployed.

Additional info:
Workaround: do not deploy kie-server together with business-central.