Rebind in NanoNamingImpl leads to security exception in Server

NanoNamingImpl rebinds the ComponentAdapters which leads to a SecurityException if the server resides on a different host than the client. This is due to a security restriction in RMI which forbinds calling bind if the method call was induced by a remote call.

The rebinding is IMHO unnessecary an can be omitted. I have attached a patch. There is no unit test for this issue because it's a functional test and I have no clue how to test this reasonably.

The pachted version is used in production by me and I found no side effects.