LOADEDMODULES bug?

[Mark L. <la...@mi...>]

In Modules 2.2beta, when I unload a package, the LOADEDMODULES env var
gets reset as I would expect. However, in Modules 3.1.0b, the
LOADEDMODULES env var does not get reset, and I can't successfully switch
to another module, since it complains!

spark,~> module unload hercules
spark,~> module load hercules
hercules/1999.2(29):ERROR:150: Module 'hercules/1999.2' conflicts with the
currently loaded module(s) 'hercules/1999.2.1'
hercules/1999.2(29):ERROR:102: Tcl command execution failed: conflict
hercules

Am I missing something, or is the module command really broken?  I looked
at the output of modulecmd directly, and I can see that it sets things
like PATH, MANPATH and _LMFILES_, but not LOADEDMODULES when I unload.

Any ideas?

-Mark