Search This in google–
what are the advantages of using weakreferences in Flex

This page link comes 2nd But the title i am getting is reeducate the great efforts done by you for this article , Just a suggestion Try to solve it :)

Its aweSome article .. Really a great tutor for all FlexDev. 10 out of 10 :)

I do think a decent compromise is to recognize which elements of a project are really worth the extra effort. If you’re making a billion instances of something then it’s time to do the necessary work. If there’s a part that never or rarely needs to get totally removed I suppose you can use weak references or–gasp–just let the memory leak go. I’m not suggesting people become “pussies” but step 1 is to notice when it matters most.

1) weak references are more expensive then strong. they take longer to process.

2) you never know when a weak reference will get garbage collected.

Now if my team is working on a project that WE built. Then yeah: RCOK DESTORY. But if we jump into the middle of a project we didn’t build where we could miss a destory or dont have time to crawl through all their code to add it then using weak references may not be a bad idea imo.

-erik