Hello there.
I gave you one piece of duff information at the start, I had not tried this on Windows until today. On Windows, it works just fine, so apologies for that.
However, I run the exact same code in my Linux environment (it's the same Eclipse workspace) and I see the problem I described here, 100% repeatable.
I tried it on the latest JDK, which is 1.6.0_16, and the same issue.
As a last resort, I used jvisualvm to attach to soapui and do some basic CPU profiling. I attached an image of the execution hot-spots.
I can't explain the hot-spots because I obviously don't know your code, but if you look at that attached image you will see the following looks a bit suspicious at least to me:
com.eviware....ModelItemIconAnimator.run() has over 8 minutes self execution time.
com.eviware....JInspectorPanelImpl.propertyChange() has just under 8 minutes self execution time.
This snapshot was taken something like ten minutes after the response XML came back and the UI jammed up.
I will find some time as soon as I can to get the latest nightly build and execute the same steps as you.
