title: What is the craic with ContainerViews? (Assertion Failed: calling set on destroyed object)
body: <p>All,</p>
  
  <p>I have searched around for an answer to this but have yet to find a good explanation and solution.  Hopefully, you can help.</p>
  
  <p>I have a route that renders an Ember.ContainerView (as opposed to a standard Ember.View).  When I transition away from this route and then back to it (either via the back button, a link-helper or just changing the url) I get the following error in the console:</p>
  
  <pre><code>Uncaught Error: Assertion Failed: calling set on destroyed object
  </code></pre>
  
  <p>I understand that a high level reason for this is that when we transition away from the route with the ContainerView, it's <code>childViews</code> are marked as destroyed.  When we transition back to the route, the problem has something to do with Ember trying to set the <code>childViews</code> back to the destroyed instances.</p>
  
  <p>I'm not exactly clear but that is the vague understanding I currently have.</p>
  
  <p>So, my questions are as follows:</p>
  
  <ol>
  <li><strong>Can you please correct my understanding of this problem if it is not correct?</strong></li>
  <li><strong>Can you please tell me how to fix this error?</strong></li>
  </ol>
  
  <p>For your convenience, I have created a <a href="http://jsbin.com/riruz/1" rel="nofollow" title="JSBin example">JSBin example</a> for your viewing pleasure.  To replicate the error, open your JS console, click on the <code>Go to Route two</code> link, then click on the <code>Go to index</code> link.  Now check your logs.</p>
  
  <p>Thanks in advance for any assistance you can provide.</p>