Bug: SoapUI fails to add REST Test Method to Test Case when using Resource solely to share parameters

[Duplicated from my EviWare/SoapUI forum post here.]

Using SoapUI 3.6.1, I ran into same problem as listed here viewtopic.php?f=2&t=4462&start=15 (which I named this topic after).
I downloaded the 3.6.2 nightly and retried. No fix.
OOI, by opening the project XML in Eclipse, I can see that despite throwing the same error, if I save, the new testStep does appear in the XML. I've tried "Resolve" (no errors), loading and reloading, restarting SoapUI. No help.
Below are more details of the problem some more and a workaround ...

SoapUI aide memoire and groovy scripting (on RTM)

A braindump (not a tutorial) on SoapUI including use of Groovy to script parameter generation!
To whet pre-jump appetites, the SoapUI primary structure:

• Project - houses...
• Methods - Create these including parameters that need populating later (I'm doing REST atm)
• TestSuite - One can only script within a test suite/case so we'll need one
• TestCases -  one for each separable chunks of work.
  Lots of choices but I've mostly used...
• GroovyScript - code to generate values (like hashes)
• PropertyTranfer - Used to copy values between scripts and calls' parameters (REST calls, etc)
• Test Request (REST/SOAP/HTTP/JDBC/AMF!) to make actual calls
• Setup Script and TearDown Script can be placed on TestSuite, TestCase, etc to also house the scripting.  (but I've generally found scripts more handy.)
• Project-wide utility methods can only be defined with a SoapUI Pro license (IIUC).  Without this, I've ended-up with some copy-and-paste re-use :-(  Shame there's no sliding scale from Community to Pro!

Full details after the break and please note this post's a WIP -- perhaps forever!  ('90s webpage, anyone? ;-) )