83,000 WeakReferences too many?

[George.S]

I'm working on a large (really large) Silverlight 4 application and right now am using a popular memory profiler to look for memory leaks and understand how the app is using memory.
Each time I navigate to, and then out of, a certain portion of the app the number of WeakReferences increases by over 22,000 each time. Yes that is 22,000 and not a typo. Thus, it is not many naviagations like this to get it up to 83,000 total WeakReferences or so.
This seems like way, way too much. Can anyone deeply experienced with the Silverlight 4 Garbage Collector confirm or deny that 83,000 weak references is too much?
Thanks in advance,
George.S

[ShortAngry]

I can't say I am deeply experienced with Silverlight 4 garbage collection but there do seem to be plenty of links around the net discussing memory issues with Silverlight:

http://luisguerrero.net/en/2010/04/30/detecting-memory-issues-with-silverlight/

http://www.isaaceckert.com/post/2011/01/06/Silverlight-4-Memory-Leaks-ManagedPeerTable.aspx