Updating an application via admin conole in domain mode leaves the application disabled in EAP 6.4.

Issue

• Updating an application in EAP 6.4 does not enable it automatically after updating it, it requires a restart or a manual "Enable" from the admin console, whereas, in EAP 6.3.x, the application is automatically enabled when it is updated via the "Replace" option.
• We are using JBoss EAP version 6.4.0 in domain mode. If we want to deploy a new version of an existing deployment we are using the “Replace” function of the management-console. Since version 6.4.0 it doesn’t work as expected. The new version is stored in the content repository but the new version is not started.
• Applications don't hot deploy in EAP 6.4.0 when using admin console in domain mode. In the JBoss console when deploying a new ear/war file the changes aren't being picked up unless we restart the Server Group. We expect application updates to be observable without a restart.