Also, just to add some clarification to this problem...
It appears that the soapUI behavior is "Each Thread is a IP/PORT", and this is desired. So basically, when I create a loadTest in soapUI, even though the TestSuite has many HTTP GETs in a row, each GET is performed by the same thread (ie User), so they all have the same TCP port.
So, it seems like something is different with the concept of the "each thread is a user" in loadUI. I notice that the naming convention in loadUI is not "Threads" but instead "Users" or "Rate". Something is different within the loadUI coding that causes the behavior to not be the same.
