ApplicationClientDeploymentService creates a one-off thread in start(). Think about whether we should improve this:

1) WFLY-17945 injects the server management executor into the service, so it could be used instead of the custom thread.

2) Should it use StartContext.asynchronous()? (No – that would cause the server to hang as the service is added by mgmt op #1 and the task executes mgmt op #2. Op #2 will block until #1 completes, and #1 won't complete if MSC is waiting for the task to complete.)