The use of the java.beans.PropertyEditorManager as a registry for java.beans.PropertyEditor instances does not work with scoped deployments as its a vm global singleton that does not work with scoped deployments, conflicting scoped deployments and redeployments. Use of the PropertyEditorManager needs to be replaced with use of a context aware org.jboss.util.propertyeditor.PropertyEditors that allows different deployments such as a scoped sar and unscoped jmx-console to use the correct PropertyEditor and clear deployment level PropertyEditor on undeployment.