Terry:
Ah, missed this long ago!
First, I have a question: 50 web forms seems like a large number. I wonder if you might be able to reduce the number of forms by defining some common types you can source via an include, or have those complexTypes that are minor variations of one another defined as abstract types? Sometimes I find lots of forms can be readily consolidated because many actually have lots of repeat code for want of includes and stronger common type definition.
The good news is this: in 2.2, we introduce the notion of a Web Project template. When you create a Web Project, you can base off a template - everything is pre-configured (content in Staging, web forms, workflow, etc.). It makes the whole process of creating a web project just a couple of clicks. What it's really doing under the covers is branching the parent web project. It's a fast and cheap way to "clone" the parent project - branching a repo does not make copies of the data - it's all virtual! (how we love virtualization).
Now, your problem may be simpler: if you are referring to XSD updates, those should auto-propogate to all web projects. The XSD is looked up from the Data Dictionary on each request.
Cheers.
Kevin