Groups with no "Browse Users" Permission are Able to Select Assignees During Issue Creation

State of problem:

1. A user (Developer) was created in JIRA and assigned to a new group (Development).
2. Development group is given the permission to Assign Issues and Assignable User.
   
3. Development group is also given the project Roles Administrators, Developers and Users.
   
4. Attempt to create an issue in JIRA. The user Developer is able to assign issues to another user.
   
5. Go to GreenHopper's Agile page, and create a new card. Attempt to assign the issue to another user. This results in a failure since the group Development is not given the global permission Browse Users.
   
6. Go back to Administration, and assign the Development group to the Browse Users global permission.
   • Before:
     
   • After:
     

• Go back to Agile, and attempt to assign a user to a new card. This time, you can browse the list of users.
  

Which begs the question: if a group is not given the permission to Browse Users, how is he able to assign issues to users in JIRA? Is this intentional?

We understand that GreenHopper doesn't allow this as it respects the Browse Users permission, but can the same be said of JIRA?

Attached is a screen-cast video of the entire replication process: http://dl.dropbox.com/u/3233473/jra25573_screencast.mpeg