Avoiding Dependency Error in Redeployment

I am using JBoss to create high available servers running 24×7 without needing the application server to be restarted if a component needs to be replaced. to fulfill this requirement, the component should be deployed in a specific manner.
A bean Interface could be needed by other beans. If the bean interface is removed from the hot deploy directory, JBoss class loader will also remove the interface definition from its interface collection. If the interface needed by other beans is missing, the JVM would generate exception.
To avoid the situation, bean Interface and Implementation should be treated as different deployment units.
The interface deployment unit is the unit that rarely changed. The interfaces should be designed well enough so hopefully it will not need to be changed.
The bean implementation deployment unit is the unit allowed to be changed often. The redeployment of this unit will not break the system dependency.