>>6,7
I was confused over the definition of iterative evidently, my thought was that it was simply a function which kept state off the call stack and as a form other than a function. With this definition my thought on the isomorphism was not that every procedure has an iterative function that can be derived from it in the traditional since, but rather that a defunctionalize procedure seemed to be necessarily iterative because you translate all recursive calls into a datastructure which you pass around. This is incorrect, yet further insight gained, terminology is important.
Anyway, EOPL is on my virtual book shelf, and I plan on reading it eventually, although I'm not exactly sure when. I've decided to relearn a good bit from scratch so I'm currently working through “The Seasoned Schemer”, hopefully I'll finish by the end of next week. One thing that really interests me about continuations is there use in making composable hygienic macros, and as you mention as a translation phase of compilers/interpreters, I think I'm awhile away from these applications though.