It holds all of the references to the dependencies strongly, which makes sense since it is a memorization helper function. It saves all the dependencies to avo

It holds all of the references to the dependencies strongly, which makes sense since it is a memorization helper function. It saves all the dependencies to avoid recomputing if the same dependency shows up any time in future. But in my case I was using an old school library where you call destroy and set reference to the instance as null, and putting that as a dependency in usMemo was a bad idea.