Reduce AM mem usage caused by storing TezEvents

This is open ended at the moment.
A fair chunk of the AM heap is taken up by TezEvents (specifically DataMovementEvents - 64 bytes per event).
Depending on the connection pattern - this puts limits on the number of tasks that can be processed.