You know if you look back at the history of ALL the large crashes in BTC, they are all associated with a speculative bubble which is popped by some kind of service-interruption at Mt.Gox. To my knowledge this is the 3rd, the first was Nov 2010, the second July 2012 and now the third is April 2013. This seems to be following a pattern of occurring every 8 months. Which shows that the community has an appallingly short memory.
By definition if a failure in infrastructure causes a panic, it's a panic, not a bubble. Speculative bubbles pop when they reach a point on the supply and demand curves that is unsustainable usually when supply is choked off for some reason. When an external force like a major selloff is the main cause it's a correction, not a bubble. This was nearly criminal negligence at best and intentional fleecing of the flock at the worst by MtGox. I say it's possibly intentional because if their intent was to provide a reliable service they could have added stop-loss orders even if they couldn't fix their server lag issues. The only real reason not to protect your clients with a stop-loss is if you intend to use or allow someone else to use the panic to clean up.