Two obvious ones I have come across are authentication and pages with frames.
For authentication, UIWebView does not handle authentication challenges automatically, it's up to the developers to handle them.
For pages with framesets, UIWebView does not keep track of the browsing history for page transitinos within frames, which may be a desirable feature. It needs a bit of fiddling to accomplish this.
