Those issues still apply for SOAP UI v4.6.4 Build Date: 20140110-2328.
Both issues make SOAP UI very hard to use for testing real requests and responses created by web services and web service clients since fake CDATA sections are misleading.
It seems like these issues are caused by "Format XML (Pretty-prints the XML)" functionality that also replaces escaped string values with CDATA sections in some situations (more than 3 tags).
For instance the following XML sequence from a WS response message:
<ns1:string><a href="s"></a><h1>y</h1><h1>z</h1></ns1:string>
is converted automatically by "Format XML" into:
<ns1:string><![CDATA[<a href="s"></a><h1>y</h1><h1>z</h1>]]></ns1:string>
It would be great if this replace behavior of Format XML can be removed or disabled from SOAP UI global preferences.