The concept of a continuous query is out side of how the sql is expressed. Or to put it differently, the sql specifices how each iteration of the continuous query should be executed. The engine starts over each time. Only ReusableExecutions are aware that they are being called multiple times within the scope of the continuous query.
As you had expressed before there is a desire for some stuff to be cached beyond a single iteration. https://issues.jboss.org/browse/TEIID-1598 provides one avenue at the translator level using the session scope. https://issues.jboss.org/browse/TEIID-2077 is another possible hook as well.
Thanks for the explanation, Steve. I was actually hoping that that's how it operated and I think it's exactly the right behavior. I didn't make it clear in my response: I was trying to find an explanation for some the behavior that Andriy is seeing. It looks like Andriy and Ramesh are working through the details, so I'll stop sticking my nose into it.