With the JES feature flag in 1.24 I did the following:
Created an environ "env1" and added user "bob" to it. At this point I had two jenv files pointing to the same environment: bob.jenv and env1.jenv. Then I called "juju destroy-environment bob". This removed the bob.jenv file and the environment record from the database, but left env1.jenv
This had the side effect of being able to juju switch to env1 (as the client goes off the .jenv files) but not being able to get the status for that environment (as it's been deleted from the State database). I was unable to create another environ named env1, even after destroying and bootstrapping the server environ - as the env1.jenv makes the client think we've already got an env1 environment.
Possible solution: When an environment is destroyed, all .jenvs connecting to that environment should be removed from .juju/environments.
Marking as incomplete as we are discussing the best approach for handling jenvs after an environ is destroyed.