Apologies that was a typo, it was actually added in RUP4 and not CU3. I corrected the thread.
Here is your workaround,
1. Create a simple personalization on the page so it creates a personalization document.
2. Export the personalization document to file system
3. Edit the document and add the following tags inside the modifications tag,
<insert after="<find the table item id after which you need to add the link>">
<oa:link id="Link" adminCustomizable="true" destination="http://www.yahoo.com"
rendered="true" scope="." serverUnvalidated="false" targetFrame="_blank"
text="Link" userCustomizable="false" viewAttr="<viewAttribute>" viewName="<viewUsgaeName>"
warnAboutChanges="true" xmlnsa="http://xmlns.oracle.com/oa"/>
</insert>
4. Import the document back to the repository and bounce the apache.
This workaround is only applicable for this case only since we had put the link item back in RUP4 the personalization modification you are doing in CU3 will hold. This should not be used for any other usecase without confirmation.