Does read-uncommitted keep all updates it is pointing to in memory?

Read-uncommitted can return a pointer to data in a WT_UPDATE that is subsequently rolled back (txnid set to WT_TXN_ABORTED). It isn't clear that the snap_min value we publish for read-uncommitted operations will always prevent such updates from being freed.