Created an attachment (id=561) [details]
valgrind-report.txt

The 2nd leak is the one of interest here (globus_i_xio_context_create)

Here are some more (hopefully useful details):   
   
The context leak seems to stem from a bug handling driver_operations. In this   
particular case, it is a write operation synthesized from a handle_cntl. In   
the callback for the write, globus_xio_driver_operation_destroy() is called,  
but the reference count for the context is not decremented because the  
operation's reference count is not 0 (the outstanding reference is the write  
callback which hasn't returned yet). 
 
joe 

Joe, can you write what client(s) did you run in addition to the container?
I tried running all tests, but it didn't show up the leakage you meant.