I scaled back the test to 1000 nodes and changed the order of steps slightly (to create a objects which broadcast packets on the network AFTER the 1000 nodes are created, rather than before). The reordering means I have a second loop to create the packet generating objects rather than combineing that step in the first loop which sets up the parameters for those objects.
Regardless, the test is proceeding, however, it will fail... memory is still being consumes at a great rate. Check out these images. The first three are from the original test setup, the last is from the adjusted setup (where the packet generators are setup after the nodes are created).
The long rise in this next image indicates that the test is now in the add a group, add nodes to the group, send command to the group, delete the group loop.
Finally, the test exhausted the allocated memory and flatlined. The test still runs though tere are a lot of nullpointer exceptions and out of bounds errors in the console log. As well, the test step numbers appear to be decrementing when in a loop.. check out this pic to see what I mean: