If evaluateObject doesn't return success, value would probably be nullptr anyway, making the only case it helps is when method exists but does not return an array. Did you really encounter a memory leak here?

While highly unlikely object is non-null and invalid, let's get this in, in case of some wacky user-defined method :)

It's mainly the reference count on object. I am going to merge this in.