Fixed memory spike from reloading repositories:

The cause was that because the UI was already bound to the model, a quadratic number of updates was being sent to all listeners as a result of items being added one by one. Listeners were instantiating UI components in response, causing the spike.

This exposes a less serious memory leak in the UI (memory usage doesn't go back down) but stops the bleeding for now.