overwriting/leaking the application's WT_ITEM value

@michaelcahill, @agorrod: here's a possible fix.

I'm expecting overwrite to usually be set which means this lookup never happens, so I didn't avoid the memory allocation inside `__clsm_lookup`; if that's wrong we could cache a WT_ITEM somewhere, or use a scratch buffer instead.

Reference #965.