Tuscany 1.6 RMI bug: ConnectException after component restart

When I have a network of components connected by RMI references,
then restarting a component will cause a java.net.ConnectException
in all dependent components on the next remote method call.
I suspect some kind of connection factory caches out-of-date information.

Example:
ServerComponent exposes service "Server" with an RMI binding on port 8777.
ClientComponent exposes service "Client" with an RMI binding on port 8666
and has a reference to the service "Server".
ClientTest is a non-SCA Java class that exercises the Client service over RMI.

Everything works fine until the ServerComponent Java process is stopped
and re-started. The tester will then fail, because the client cannot
re-establish the connection to the server.

I attach a zip-file with the example. Steps to reproduce the problem:
Run ServerLauncher
Run ClientLauncher
Run ClientTest
Stop process in which server is running
Re-Run ServerLauncher
Re-Run ClientTest