Undeploy Issue with Clustered Stateless Session Beans with HTTP(S) Remote Bindings

Combination of a clustered annotation and a HTTP(S) based remote proxy on a stateless session bean causes the bean to leave the HTTP(S) remote proxy binding still deployed after an undeploy operation, breaking re-deploys of the bean.

For example:

<session>
<ejb-name>TestBean</ejb-name>
<remote-binding>
<jndi-name>TestBean/remote</jndi-name>
</remote-binding>
<remote-binding>
<jndi-name>TestBean/remotehttp</jndi-name>
<client-bind-url>
http://${public.firewall.address}/servlet-invoker/ServerInvokerServlet
</client-bind-url>
</remote-binding>
<clustered>true</clustered>
</session>