Having a JIT requires you to execute writable memory which is a privilege given on a per-process level. So for an embedded webview to be able to do it, your app would need it, but third party apps are never allowed this.
It's possible that they changed UIWebView to spawn a background process for the actual rendering, but I guess we would have heard about that (we haven't we only heard about homescreen links now being JITed)
Trying to mark memory as executable will cause your app to be terminated. Jumping into non-executable memory will also cause your app to be terminated.
Aside of protecting you (as a user or as a developer) from a big class of security issues, this also ensures that nobody ever gets to run code that's not loaded from the App Store (and thus would generate revenue without giving a share to Apple).
It still is. The JIT was enabled for "pinned" web applications (added to the home screen), but for the JIT to be enabled the whole process needs to be allowed to execute code from writable memory. There's absolutely no way Apple is going to allow arbitrary applications to do that.
As pilif notes, a workaround would be to have UIWebView's content exist in a separate, JIT-able process.
I'm not sure this is still the case in iOS5.