We try hard to prevent it, but yes, there are cases where a retentive value in the image register can get stuck in such a way as to cause trouble. I'm pretty certain this is only in cases where the memory map is changing...old stuff in memory getting mapped to new locations. But as a general rule, it is best to flush the memory when starting something new.
That said, if anyone can demonstrate a case where an instruction gets stupid and it isn't a case of changing memory config without clearing the image register, we really need to know it.