A failed singleton bean redeployment causes "Already registered" errors

If a deployment of a singleton bean fails and the user then redeploys the application (after fixing the original error), the redeployment fails with "Already registered" errors for the singleton container.

Please refer to the referenced forum thread for the entire details, including the root cause of this issue.