Ok, we've been digging deep on this, and determined it's most likely the server node checkins causing the memory leak. It appears the go routines are not being garbage collected. We're still digging in further to get it fixed.