Memory ballooning creating sites

Question

I am creating 100 sites using PowerShell something like this:
Start-SPAssigment -Global$web = New-SPWeb $url –Name $Name –UseParentTopNav -description $description -ea stop
$web.ApplyWebTemplate($Id["SiteTemplate_1"])Stop-SPAssignment - Global
I am seeing memory ballooning. I am running this on a test system at the moment but I can't actually create 100 sites without getting system out of memory errors. The powershell process itself is using 6 GB by this point. I tried using advanced assignment
like this:
$spO = Start-SPAssigment
$web = $spO | New-SPWeb $url –Name $Name –UseParentTopNav -description $description -ea stop
$web.ApplyWebTemplate($Id["SiteTemplate_1"])
Stop-SPAssignment $spO
It made little to no difference. If I don't use SPAssignment and dispose of the spWeb object explicitly I don't see the problem.  So my questions are does SPAssignment actually work as intended? Am I using it wrong? My samples are simplified from what
I am actually doing and to be honest wrapping code blocks in SPAssignment -global is easy but pointless if it doesn't work correctly...
Thanks
Darrell

Answer 1

Just to be clear this is PowerShell I am talking about...
This technet article: http://technet.microsoft.com/en-us/library/ff607664(v=office.15).aspx disagrees with you.
Quoted here:
The Start-SPAssignment cmdlet properly disposes of objects used with variable assignments.
Large amounts of memory are often required when SPWeb, SPSite, or SPSiteAdminsitration objects are used. So the use of these objects, or lists of these objects, in Windows PowerShell scripts
requires proper memory management. By default, all Get commands dispose of these objects immediately after the pipeline finishes, but by using SPAssignment, you can assign the list of objects to a variable and
dispose of the objects after they are no longer needed. You can also ensure that the objects remain as long as you need them, even throughout multiple iterations of commands.
Cheers
Darrell