Issue type is not reset to the default one when creating ticket in a new session

Summary

According to the KB articles below, JIRA should reset the issue type to the default one when creating ticket in a new user session. However in the latest version of JIRA, JIRA will still remember the last issue type when creating ticket in the same project after user has opened a new session.

• https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-707986896.html
• https://confluence.atlassian.com/jirakb/default-issue-type-when-create-an-issue-301662415.html

Steps to Reproduce

1. Set a default issue type in project settings.
2. Create a ticket with an issue type that is different from the default one.
3. Logout JIRA and login again or open JIRA in another browser.
4. Click Create button to create a ticket in the same project.

Expected Results

In the issue creation form the issue type should be reset to the default one.

Actual Results

In the issue creation form the issue type remains the one that has been selected in step 2.

Notes

This issue cannot be reproduced on a JIRA 6.3 instance.
When changing the project to another one, JIRA will still remember the issue type if the target project also contains the selected issue type.