Just in case others come across this question ... the "obvious" solution is to make wordApp a property of a custom handle object, and to do wordApp.Quit() in the destructor of the object.
I was hoping for a non-object based approach, however, so if anybody has any insight, please let me know. Like maybe a way to find an existing instance of Microsoft.Office.Interop.Word.ApplicationClass.